Table 4–1: Transition command actions
|
Database type
|
Database state
|
Online or
offline
|
Description of transition performed
|
|
Source
|
Database is newly enabled.
|
Offline
|
An error occurs because the database is newly enabled.
|
|
Source
|
Database is newly enabled.
|
Online
|
An error occurs because the database is online and has never been replicated.
|
|
Source
|
Database has been replicated.
|
Offline
|
The database is transitioned as instructed in the repl.properties file.
|
|
Source
|
Database has been replicated.
|
Online
|
In order to transition a source database in this state, the replication server must be communicating with the replication agent to communicate a transition and failover request to the replication agent.
|
|
Target
|
Database has been replicated.
|
Offline
|
In order to transition a target database in this state, the database cannot be newly transitioned.
|
|
Target
|
Database has been replicated.
|
Online
|
In order to transition a target database in this state, the following conditions must be met:
- The replication agent cannot be communicating with the replication server.
- The replication agent must be in pre-transition.
- All source AI extents must be applied to the target database by using
dsrutil db-name -C applyExtent.
You must explicitly perform this step, possibly multiple times depending on the number of source AI extents.
|
|
Normal
|
–
|
Online
Offline
|
An error occurs because the database is not enabled for replication.
|